Upgrade notes

Starting in 7.2.3

Hardening of logging configuration

HCL Launch now uses Log4j 2.x. A new feature is introduced that provides users an easy-to-use UI for logging configuration, and better security.

See documentation, Logging.

Removed $productName/java.home from agent: The $productName/java.home property is removed from agent properties file. Upgraded agents are compact agents that does not require Java home property.
Updated the sshInstallAgent/installNewAgent CLI endpoint as POST request: For security purposes, the sshInstallAgent/installNewAgent CLI endpoint is updated to post the install agent informaton without the sshPassword.

Starting in 7.2.2

The agent relay property agentrelay.http_proxy.use_rabbit=true introduced in V7.0.5 is now obsolete and deprecated.

Starting in 7.2.1

Announcing end-of-support for WinRS

All our customers should note that starting May 2022, HCL Launch will deprecate WinRS as a supported utility, formally ending our WinRS support.

IBM Java not bundled

In the v7.2.0 upgrade note, Java 8 end-of-support was announced. It is to be noted that IBM Java (JRE/JDK) will not be bundled with HCL Launch v7.2.1.0 and later.

If you are using the bundled JRE, you need to migrate to the other supported runtimes. For supported runtimes, refer to the documentation or software compatibility report.

Starting in 7.2.0

Announcing end-of-support for Java 8

All customers should note that we are officially announcing end-of-support for Java 8 starting June, 2022. Additional information on alternative Java platforms will be communicated later.

End-of-life for JMS communication

Agents and relays that use the JMS communication protocol will no longer be able to connect to the HCL Launch server. Agents and Relays will need to be migrated to the Web communication type in order to connect. You can use agent configuration templates to migrate from JMS communication to web communication.

Starting in 7.1.2.10

Server/agent version mismatch: You will notice the inconsistency between the versions of HCL Launch server and agent installation files. Know that the version mismatch, server v7.1.2.10 and agent v7.1.2.9, will not cause any installation or upgrade problems.

Starting in 7.1.2.7

Updated the sshInstallAgent/installNewAgent CLI endpoint as POST request: For security purposes, the sshInstallAgent/installNewAgent CLI endpoint is updated to post the install agent informaton without the sshPassword.

Starting in 7.1.1.2

Running an application process

The CLI endpoint /cli/applicationProcessRequest/request has been corrected from PUT to a more appropriate method POST. The PUT method is obsolete, but it is still allowed in the newer HCL Launch versions. Note that the HTTP POST should be utilized starting version 7.1.1.2 and the scripts should be updated from PUT to POST to avoid running into issues.

An example documentation can be found here:

Run an application process in v7.1.1.1 and before (obsolete):
```
PUT https: // {hostname} : {port} /cli/applicationProcessRequest/request
```

Run an application process in v7.1.1.2 and later:

POST https: // {hostname} : {port} /cli/applicationProcessRequest/request

Starting in 7.1.1.1

Process Designer Explorer mode removed: Starting with V7.1.1.1, the Process Design Editor user interface no longer contains the Explorer mode.

Starting in 7.1.1

JMS agents when connected to the server in your environment, a warning message is displayed. You are prompted to begin the migration of JMS agents to a web format. See Migrating Agents to Web for more information.

A new version of Hibernate, v5.4.20, is included. Hibernate v5.4.20 may require newer versions of the JDBC driver in order to function properly. Ensure that you have a driver version of at least 4.2 that works with your database to be compatible with Hibernate v5.4.20. This upgrade also removes the hibernate.dialect property from the installed.properties file as the new Hibernate version itself determines the dialect.

All our Mainframe customers should note that with the HCL Launch 7.1.0.2 release, we are officially announcing end of support for HFS codestation as an Artifact Repository on May, 2021. All users are strongly encouraged to migrate to the HCL Launch’s in-built artifact repository Codestation. They can also migrate to supported third party artifact repositories Artifactory^TM or Nexus^TM (supported from version 7.0.5)

Starting in 7.1.0.0

The Safari browser is no longer supported. The Chrome, Firefox, or Edge can be used.

The Show Inactive option has been removed. You cannot view inactive objects in their respective tables. The Active field is still included in the JSON representation of objects and now reflects whether or not the object has been deleted. Logging information is now written to deployserver.outinstead of the stdout file.

Upgrading from UrbanCode Deploy

If your are upgrading from UrbanCode Deploy to HCL Launch, make note of the following changes:

The Show Inactive option has been removed. You cannot view inactive objects in their respective tables. The Active field is still included in the JSON representation of objects and now reflects whether or not the object has been deleted.
Logging information is now written to deployserver.outinstead of the stdout file.